Polygon Cross-Chain Gateway & Route Specifications
Bridging to Polygon moves an asset's usable representation between two separate blockchains — it is not a swap on one chain.
Read more
Polygon PoS is an EVM-compatible Ethereum sidechain (chain ID 137) with its own consensus and POL as gas, so you can use the official PoS bridge or a third-party route, deposit or withdraw, and pay gas on both sides. This page is an independent informational dashboard: it compares routes but never holds your keys or operates the underlying bridges.

What is Polygon PoS Bridge?
Polygon Bridge connects Ethereum and Polygon PoS by moving an asset's usable representation between chains; the official PoS bridge locks the source asset in escrow contracts on Ethereum and issues the mapped representation on Polygon, while third-party routes use different liquidity, relayer, or message-validation designs.
The native route works without market liquidity and supports ERC-20, ERC-721, and ERC-1155 assets; native POL deposits arrive as native POL. The ERC-20 token standard explains the transfer and approval interface used by fungible tokens. The PoS bridge connects Ethereum and Polygon PoS only; it does not bridge directly to Polygon zkEVM.
How bridging works
Bridging works by selecting the source network, Polygon PoS as destination, asset, amount, and recipient, reading the route and estimated costs, and submitting the route's transactions from a self-custody wallet. On the official route, a deposit locks the asset on Ethereum and mints its mapped token on Polygon; a withdrawal burns the Polygon representation, waits for a validator checkpoint to land on Ethereum, and then uses a separate claim transaction on Ethereum to unlock the escrowed asset.
An approval is a separate permission for the bridge contract to move a token on your behalf. That lock-and-mint or burn-and-claim pattern is the native case of the broader blockchain bridge model; third-party routes may instead use liquidity pools, relayers, or their own message validation.
Depositing to the destination
Depositing from Ethereum to Polygon usually takes minutes after the Ethereum transaction receives its required confirmations and the bridge processes it. The deposit and any token approval use ETH on Ethereum; once the mapped asset arrives, actions on Polygon use POL for gas. That gives the deposit direction a two-chain funding path: ETH for the source-side transaction and POL for the destination-side transaction.
Withdrawing back
Withdrawing from Polygon to Ethereum is a three-stage flow: burn the Polygon representation, wait for a Polygon validator checkpoint, then submit a separate claim transaction on Ethereum to release the escrowed asset. Checkpoints normally arrive roughly every 30 minutes; after the checkpoint is included, the claim uses ETH gas, and total time also depends on congestion and how quickly the claim is submitted. The official bridging guide shows the claim flow. The withdrawal is tracked by its burn transaction, so a second burn is not a new step in the same withdrawal.
Time and fees
Bridging costs are network gas plus any fee built into the selected route's quote. You pay ETH on Ethereum for approvals, deposits, and withdrawal claims, and POL on Polygon for burns and general use; Ethereum gas changes with congestion, so the same deposit can cost different amounts at different times. The official PoS bridge charges no protocol cut on top of gas, while third-party bridges typically add a provider or liquidity fee to the quoted receive amount. Timing follows the same split: deposits are usually minutes, while withdrawals follow the checkpoint cycle and then the claim.
Is Polygon Bridge safe?
Polygon Bridge carries smart-contract, validator and checkpoint, upgrade-governance, network, and user-error risk. The PoS bridge uses upgradeable contracts governed through multisignature controls, and its contracts escrow assets while mapped representations circulate on Polygon; confirmed bridge transactions cannot be reversed. Fake bridge domains are a standard phishing play, so before signing verify the domain, source and destination networks, token contract, approval scope, and recipient address; treat ads or DMs offering bridge “support” as phishing until proven otherwise. If an approval was granted to the wrong contract, use a known-good tool to revoke it; MetaMask's guide to revoking token approvals explains that separate permission step.
Problems and fixes
Bridging problems are usually a network mismatch, missing destination gas, or a withdrawal that has not reached its claim stage. Wrong network: if the wallet is on Ethereum while the interface expects Polygon (chain ID 137), or the reverse, switch networks and reload. No destination gas: if the asset arrived but there is no POL to move it, fund the Polygon wallet before the next transaction. Pending withdrawal: if the burn is complete but the checkpoint has not landed, or the Ethereum claim is still unsubmitted, check the withdrawal status and submit the claim.
Verified Contract Gateway: 0x8453000000000000000000000000000000000000 (Chain verification active)
Polygon FAQ
Is this the official Polygon Bridge site?
No. This is an independent, non-custodial informational dashboard that compares bridge routes; it does not hold private keys or operate the underlying bridge contracts.
How long does bridging to Polygon take?
Deposits from Ethereum to Polygon typically complete in minutes, depending on confirmations and congestion. Withdrawals back to Ethereum take longer: they wait for a validator checkpoint (normally submitted roughly every 30 minutes) and then require a separate claim transaction on Ethereum.
How do I bridge to Polygon?
Select Ethereum as source and Polygon PoS as destination, choose the asset and amount, connect a self-custody wallet, and submit the deposit or withdrawal route. A deposit locks the asset on Ethereum and issues the mapped token on Polygon; a withdrawal burns that representation, waits for a checkpoint, and then uses an Ethereum claim.
Do I need POL for gas on Polygon?
Yes. Polygon PoS uses POL for gas, while Ethereum uses ETH: ETH covers Ethereum deposits, approvals, and withdrawal claims, and POL covers burns and other Polygon transactions. The current POL token reference is available on CoinGecko's POL page.
Is bridging to Polygon safe?
Polygon Bridge's safety profile is defined by its smart contracts, validator checkpoints, governance controls, network conditions, and signing choices; the dedicated safety section lists the checks.
What is the difference between the native bridge and third-party bridges?
The official PoS bridge locks assets on Ethereum and mints mapped tokens on Polygon without relying on market liquidity; withdrawals use checkpoints and an Ethereum claim. Third-party bridges use liquidity pools, relayers, or other validation, which can change speed and fees but also changes the trust assumptions you accept.
Notes before you use Polygon Bridge
Use the direction-specific timeline: deposits to Polygon are usually quick, while withdrawals require the checkpoint wait and a separate Ethereum claim; keep ETH for Ethereum transactions and POL for Polygon transactions.
A withdrawal with no immediate Ethereum arrival is normally waiting on the checkpoint or the claim transaction, not missing from the burn flow.
Before signing, confirm in one pass: the source and destination networks (Ethereum chain ID 1, Polygon chain ID 137), the token contract, the approval scope, the recipient address, the ETH needed for the deposit or claim, and the POL needed on Polygon.
Everything above reflects the documented bridge mechanics, checked against official sources, last reviewed 21 July 2026.
Independent reference — confirm the route in your own wallet. A self-custody wallet signs the transactions, while bridge contracts handle escrow and mapped representations.